Is fixed

Could you please clarify the intent of this PR?

In particular:

• Does it in any way revert the behavior introduced in Lambda: support for excess energy specified in negative numbers #21972?
• After this change, will the Lambda setup still support the “negative excess” values as described in the Lambda Modbus specification?

Fall 2: Negative Energieüberschussmessung: Der Energiezähler misst die Energiemenge in der Netzzuleitung das Gebäudes. Die Wärmepumpe versucht die Überschüssige Energie (PV Ertrag abzüglich aller eletrischen Verbraucher im Gebäude), welche ins Netz eingespeißt werden muss, zu verbrauchen. Negativ bedeuted hier, dass bei Messung eines Überschusses (Strom wird ins Netz eingespeißt) ein negativer Wert angezeigt wird. "

For reference, from the Lambda Modbus Spec - Register 102

Name

102 Actual power (input or excess)

Data Format

UINT16 or INT16

Register desciption

Actual input power [UINT16 (min = 0 W; max = 65535 W)] or actual excess power [INT16 (min = -32768 W; max = 32767 W)] (depends on settings in Module)

(source: https://lambda-wp.at/wp-content/uploads/2025/02/Modbus-Beschreibung-und-Protokoll.pdf)

Hi,
the current implementation of the Lambda heatpump does not work and using the "negative excess" configuration of Lambda is not appropriate for EVCC. The reason is, that EVCC by design gives the availabe power to the Lambda heatpump and does the excess-calculation itself. That matches the "E-Eintrag" or "Energy-Input" setting of the Lambda.
So with "negative excess" setting the Lambda will not shutdown because of no excess energy, because the own consumption will be added to this value... That does not make sense in combination with EVCC
There was a exhaustive discussion regarding that and this PR is result of that:
#20179 (reply in thread)

Best regards,
Florian

I've left the BC marker for heads-up, but it really isn't breaking as the old configuration was broken anyway.

My Lambda heat pump is configured with “Neg. E-Überschuss” — a fixed setting that I cannot change myself; it can only be adjusted by Lambda or someone with elevated access.

I’ve been running evcc in this configuration "excess: minus" for about a week, and the test phase has looked quite positive so far. While I haven’t done exhaustive testing, here’s what I’ve observed:

• The “excess loading” indicators on the Lambda turn on when excess energy is reported from the SolarEdge Hybrid Inverter (or its associated smart meter, to be precise)

• They turn off when I plug in my car — since the wallbox has higher priority, evcc correctly redirects excess energy to it

• Whenever I’ve checked Lambda’s Energie-Management panel, the numbers looked correct and I haven’t noticed anomalies

Could you please explain what is actually fixed by removing the "excess: minus" option?

Removing this parameter does break my setup, as the Lambda expects negative values in “Neg. E-Überschuss” mode.

@fzahn @andig @premultiply

@anbie I see your problem. Please contact your installer to get the level2-password for the lambda, which is required to change the setting to "E-Eintrag".
the setting "excess: minus" is not working properly, as the Lambda is doing own calculation of available power, which conflicts with EVCCs approach.
The details are discussed in the discussion-thread I mentioned above, especialy in this post:
#20179 (reply in thread)
Short summary: with excess: minus the Lambda is starting properly, if there is sufficient pv-excess-power, but it does not stop, when evcc sends "0", as it calulates that as "0+ own consumption". With E-Eintrag that is not the case.

So strongly recommend to have your installer change the setting to E-Eintrag (or ask Lambda-support to do that for you, they seem to have a good support)

@anbie Irrespective of this change, your current installer settings just don't fit how evcc works. This is already a problem without this PR, hence doesn't make a difference. If you're happy with how it's working (though not perfectly) just leave it as-is.

@andig
Thanks for the quick response!

I’m pretty sure that “just leaving it as-is” will actually stop working once this PR is shipped. This change removes the scale statement from the setmaxpower section in the template:
scale: {{ if eq .excess "plus" }}1{{ else }}-1{{ end }}

Without that, negative numbers will no longer be generated and sent to Lambda’s register 102. Since my Lambda is in “Neg. E-Überschuss” mode removing the scale will break the current working but not perfect behavior in my setup.

@anbie autsch, danke für den Hinweis. As discussed, your setup is "wrong" but I also realise you can't fix it. I'd suggest we add scale as advanced parameter like this:

params: 
  - name: scale
scale: {{ if eq .excess "minus" }}-1{{ else }}{{ .scale }}{{ end }}

@fzahn wdyt?

We can also leave out the minus and just add a new scale param

Hi,
i will implement that and push the change in a few minutes. I will add a description, that this parameter is normally not needed and should not be touched.

Regards,
Florian

I opened a new PR for that change. I was not able to reuse the excess-parameter, when it was set to deprecated. so I have removed the deprecated setting and made the parameter excess advanced. So we now have the backwards -compatibility